Skip to content

Conversation

@holgerd77
Copy link
Member

When experimenting along #3694 I realized that (re-)adding the Common parameters with updateParams() comes with a somewhat significant performance cost and often - e.g. for a shared Common in Client - the addition is not necessary since the parameter set is already there.

This PR adds the ability to give the parameter set a name which is then checked for along further additions to void re-adding unnecessarily.

The PR also removes the resetParam() method. This was a hypothetical method I added, because I thought it might be useful for someone. Seems overblown to me now (respectively we can always re-add), we ourselves use this method nowhere in the monorepo.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 2.

Benchmark suite Current: e738cab Previous: 9856f66 Ratio
Block 9422905 7375 ops/sec (±1.76%) 37877 ops/sec (±1.73%) 5.14
Block 9422906 7203 ops/sec (±1.17%) 35937 ops/sec (±3.35%) 4.99
Block 9422907 6974 ops/sec (±3.99%) 36656 ops/sec (±1.46%) 5.26
Block 9422908 6951 ops/sec (±3.63%) 35733 ops/sec (±1.60%) 5.14
Block 9422910 6616 ops/sec (±4.29%) 34971 ops/sec (±1.78%) 5.29

This comment was automatically generated by workflow using github-action-benchmark.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants